Hey there, just checking up on this PR as it was ready to merge a month ago? Is there a reason it hasn't yet? \cc @InpsydeNiklas

@alexflorisca We found some remaining edge-case issues where incorrect buttons were displayed in the editor, which seemed more difficult to resolve. However, we merged this now and will include it with #2448 in the upcoming 2.9.4 update.

Thanks @InpsydeNiklas. Just to be annoying, I think the best UX would be to render the PayLater button as a separate button, if it's enabled in the backend. Otherwise the merchant and shopper UX will be different!

Editor:

Frontend:

(You can see similar discrepancies with WooPayments too).

It would be great to address this too.

@alexflorisca I completely agree! Disabling the non-PayPal buttons (which also includes Venmo) is more of a temporary workaround to prevent the layout in the editor from breaking.
The problem is that the buttons rendered in the editor are using the PayPalButtons component from the PayPal React library. However, as far as I am aware, this component currently does not allow us to split the buttons into individual ones, like how it works in the frontend. We continue to look for ways to make it work, but it won't be ready for this release cycle, so we settled on this workaround for now.

Splitting may be possible (or we can try again to use the same library as in frontend), but the main problem is determining which buttons are available (e.g. for the merchant/shop country).

In frontend we use canMakePayment with async promises, but in editor it is not called for some reason.

So unless there is a way to get something like canMakePayment in editor, we would need to figure out some other way to determine the buttons availability earlier (before the express methods registration, e.g. on the server side) without the PayPal JS SDK.